Fix deploy setup script #2829
Merged
Fix deploy setup script #2829
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
casey
force-pushed
the
fix-deploy-setup-script
branch
from
1f86733 to
b791d57
Compare
raphjaph
approved these changes
Dec 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This started with me trying to fix HTTP/2, and ended with me redeploying testnet and signet.
Because we now might need to deploy from branches on
casey/ordorraphjaph/ordwhile developing, I added aremoteargument to the deploy recipes, which takes a github repo that defaults toordinals/ord.This also updates the deploy script to install
curl, which wasn't present on the VPS, andlocales-all, which gets rid of a missing locale warning.testnet.ordinals.netandsignet.ordinals.netare now up.